Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1393

reference: 614-tree-1
name: 1393
tree-preservation-order: undefined
614-tpo-1
uprn
address-text
point: POINT (-1.023504 50.881094)
geometry: MULTIPOLYGON (((-1.023475 50.881091,-1.023481 50.881101,-1.023487 50.881105,-1.023503 50.881109,-1.023520 50.881106,-1.023527 50.881102,-1.023531 50.881097,-1.023532 50.881091,-1.023531 50.881086,-1.023527 50.881081,-1.023521 50.881077,-1.023513 50.881074,-1.023504 50.881073,-1.023487 50.881076,-1.023481 50.881080,-1.023477 50.881085,-1.023475 50.881091)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL